1 Purpose

The computer-based programming portion of an exam is designed to assess your ability to construct code (entirely on your own) that conforms to a specification. This includes your ability to use code construction tools, design simple algorithms, translate those algorithms into a programming language, package the code, test the code, debug the code, and, to a limited extent, deploy the code (specifically, use the course submission system).

2 Collaboration

This portion of the exam is "open book" but you must work entirely on your own (without assistance from the instructor or teaching assistants). The source code you submit must be entirely your work; no part of it may be the work of anyone but you.

The source code you submit must be written entirely during the exam period. The use of any pre-existing code (other than that provided as part of the exam) will be considered a violation of the Honor Code.

3 Delivery

Each exam will be delivered as a Canvas "assignment". It will become available at the scheduled meeting start time and will remain available until the scheduled meeting end time.

4 Submission

All code must be submitted electronically using Autolab. Each question will have a distinct "Assignment" on Autolab (e.g., E1Q1 and E1Q2 under Exam1). For each question, you must submit a .zip file containing just your .java files for that question. The .zip file must not contain any directories/folders (i.e., the .zip file must be organized as it has been for programming assignments).

No limit will be placed on the number of submissions but, obviously, you must complete the exam during the scheduled exam period and submissions waste time. So, you should write your code as if you will only have time to submit each question once or twice.

You should assume that Autolab will not provide "hints". In other words, the submission system will be "grading" your submissions not helping you debug them.

No submissions will be accepted after the end of the scheduled exam period. So, make sure you submit an answer for each question before the end of the scheduled exam period. Your last submission is the one that will be graded (so don't make spurious changes after your first submission -- such changes may lower your grade).

5 Grading

Your answers to some questions (though not all), will be verified by Autolab using multiple tests. Hence, if your code passes some tests but not others, it is possible to earn partial credit on some questions.

It is possible that your grade on the computer-based programming portion of an exam will be lower than the grade you receive from Autolab (if, for example, your code is poorly designed, poorly implemented, or inelegant). In other words, though style defects will not reduce your grade, other aspects of quality may.

It is also possible that your grade on the computer-based programming portion of an exam will be lower than the grade you receive from Autolab (if, for example, your code is correct but you submit it incorrectly).

6 Getting Help

I will be available for clarification questions only, during the scheduled meeting time via the normal course telepresence tool (at the "Office Hours" meeting code) and via email.

7 If Something Goes Wrong

If something goes wrong, don't panic. Try and record your work (e.g., by cutting and pasting into a word processing document or by taking a screen shot) and email it to me. If you are unable to record your work, still send me an email explaining the situation.